Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ruby upgrade to 3.3 #25

Closed
wants to merge 1 commit into from
Closed

Conversation

nikhil2611
Copy link

Description

Ruby upgrade to 3.3 and chef to latest - 18.5

Issues Resolved

Check List

  • New functionality includes tests
  • All tests pass
  • RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)

Copy link

Copy link
Collaborator

@tpowell-progress tpowell-progress left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3.0 is still supported in Chef 18.

@@ -25,7 +25,7 @@ Gem::Specification.new do |s|
s.name = "berkshelf"
s.require_paths = ["lib"]
s.version = Berkshelf::VERSION
s.required_ruby_version = ">= 2.7.0"
s.required_ruby_version = ">= 3.3"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will break everything that depends on it. ">= 3.0" is the best we can do.

if RUBY_VERSION.match?(/3.0/)
s.add_dependency "chef", "~> 17.0" # needed for --skip-syntax-check
elsif
if RUBY_VERSION.match?(/3.3/)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chef 18 and 3.3 are by definition not going to be paired together unless installed as a gem. Chef 18 supports Ruby 3.0 for AIX and Ruby 3.1 for other platforms.

@tpowell-progress
Copy link
Collaborator

We need to have a discussion about how to go about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants